Performing the Import Data Process
- Merchant initiates a request to our team for data import
- We will share our PCI Attestation of Compliance (AoC) certificate to the merchant
- Merchant requests a data export (for both customer records and associated payment data) from their current payment processor, by providing Vaultera switch’s PCI AoC certificate
- We will provide our public PGP key for the merchant’s current payment processor to encrypt their export data
- An encrypted CSV file containing all the export data needs to be sent through SFTP by the merchant’s current payment processor
- We will import the data
- Post migration of data, we will send updated customer-payment method reference IDs to the merchant
Import File Format
The CSV file for import should be formatted in accordance with the following requirements:- The first line contains the names of the fields
- Each subsequent line should contain the fields for a single record
- Delimit rows by a single newline character
\n(not\r\n) - Delimit columns by
, - Leave empty fields entirely empty (no character in between delimiters). You must not denote a missing field with NULL, N/A, or any other value
- Fields can’t contain commas or newline characters (
\ror\nor,) within a field- Example of what to avoid:
1st Ave\nApt 1
- Example of what to avoid:
- All rows must have the same number of columns
- Field names and values are case-sensitive
- Multi-line fields are not allowed
- Save the file in UTF-8 format (to support non-western characters)
- Encrypt the file using the public PGP key provided by Vaultera switch
To Import Card Data
Required Fields
| Field | Description |
|---|---|
card_number | Primary Account Number (PAN) of the customer card |
card_expiry_month | Card expiry month |
card_expiry_year | Card expiry year |
payment_instrument_id | Unique reference ID of payment method saved (PSP token) Note: This is required for mapping to Vaultera Switch payment_method_id |
original_network_transaction_id | Original Transaction ID of the first transaction where the customer signed up for recurring payments. For example: Visa - Visa Transaction ID, Mastercard - Mastercard Trace ID. Note: This is only required for connector agnostic MIT |
Optional Fields
Note: Billing details are mandatorily required if AVS (Address Verification Service) check is enabled.| Field | Description |
|---|---|
name | Name of the customer |
email | Email ID of the customer |
payment_method | Payment method used by customer (e.g., card - for cards import) |
payment_method_type | Payment method type used by the customer (e.g., credit/debit) |
card_scheme | Card network (e.g., Visa, Mastercard, American Express) |
phone | Customer mobile number |
phone_country_code | Country code of customer mobile number |
billing_address_first_name | Customer first name for billing address |
billing_address_last_name | Customer last name for billing address |
billing_email | Billing email ID of the customer |
billing_address_line1 | Street name/Address Line 1 of the billing address |
billing_address_line2 | Locality name/Address Line 2 of the billing address |
billing_address_city | City of the billing address |
billing_address_state | State of the billing address |
billing_address_zip | Postal code of the billing address |
billing_address_country | Country of the billing address |